Repository navigation
fix!: retire arbitrary Native SQL execution - #18
Merged
Merged
Conversation
marianfoo
marked this pull request as ready for review
August 6, 2026 12:51
13 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
Close BASE-SEC-002 by removing the externally controlled Native SQL execution boundary and unsupported
C_DB_EXECUTEkernel call.Changes
NATIVEunconditionally and remove its dispatcher/executorValidation
npm ci: 0 vulnerabilitiesnpm test: green, 0 configured abaplint findingsSTATUS010remains BASE-BUG-007Security and compatibility
This intentionally removes the legacy Native SQL capability. Replacing the unsupported call with ADBC would retain the arbitrary-statement injection boundary, so the command now fails closed. The source remains compatible with the SAP_BASIS 750 syntax floor.
Release impact
This must produce a major-version signal in Release Please because existing installations that enabled the
NATIVEcommand lose that capability.BREAKING CHANGE: The
NATIVEcommand and its arbitrary Native SQL execution path are no longer supported.